Repository navigation
[vote] Models changes for new vote service - #575
Conversation
|
Yes, quite a lot. |
|
Os-go: OpenSlides/openslides-go#312 |
|
@vkrasnovyd Do we need an update for the backend as well? |
|
Minor: re-generating the models and adjusting some tests. Will do today. |
|
Please wait one moment. We want to change the model again. We want to have both, Please also check, that if a meeting_user gets deleted, it does not delete the poll_option, but only the field We want to do the same for |
It should be defined in meta, in
|
|
I added all models changes, that we have discussed yesterday in here, so we can fix them in the services without merge conflicts. |
|
@ostcar as far as I understood, according to the new concept |
|
The current value of openslides-meta/collections/poll.yml Lines 92 to 94 in 73d0bf1 I don't know the format of it. In the new system, it is a list of numbers (a relation-list field) |
|
os-go, autoupdate and vote service are ready. @bastianjoel and @vkrasnovyd pls tell, when the other services are ready, and we can merge this into the feature/vote branch |
|
backend will be ready in the first half of next week. |
|
@bastianjoel and @vkrasnovyd Here are the changes as discussed |
| content_object_id: | ||
| type: generic-relation | ||
| reference: | ||
| - meeting_user | ||
| - user |
There was a problem hiding this comment.
- During migration: if meeting_user exists, use it, if not - use user.
- On meeting_user delete - change relation to user.
- On meeting_user create if user has poll_options in the polls of the corresponding meeting - don't change content_object_id from user to the new meeting_user.
Is it correct?
There was a problem hiding this comment.
- You can just always use the user if it is easier.
Co-authored-by: Bastian Rihm <me@bastianjoel.de>
Co-authored-by: Bastian Rihm <me@bastianjoel.de>
|
Added
|
|
backend: OpenSlides/openslides-backend#3734 |
@bastianjoel Do you need changes on the client?